Skip to content

Conversation

@Noremos
Copy link
Contributor

@Noremos Noremos commented Apr 2, 2025

No description provided.

{
return SectionType::DATABASE_REGEX;
}
else if (name == "service")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change will break existing trace configs. I strongly disagree.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When reviewing #8427 I missed that trace-specific routine was put into common class.
It is ConfigFile::Parameter::parseSectionKey() and related enum class SectionType.
I think both must be moved out of ConfigFile::Parameter into TraceCfgReader.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think both must be moved out of ConfigFile::Parameter into TraceCfgReader.

+1

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change will break existing trace configs. I strongly disagree.

Existing configurations are using the key 'services'. It was my mistake in the original PR where I incorrectly set the key as 'service'."

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When reviewing #8427 I missed that trace-specific routine was put into common class. It is ConfigFile::Parameter::parseSectionKey() and related enum class SectionType. I think both must be moved out of ConfigFile::Parameter into TraceCfgReader.

I have moved the method

@dyemanov dyemanov merged commit 08cb3f9 into FirebirdSQL:master Apr 3, 2025
24 checks passed
@hvlad
Copy link
Member

hvlad commented Apr 3, 2025

I don't think that PR with unresolved change request should be merged.
Also, there was no need in hurry in this case.

@dyemanov
Copy link
Member

dyemanov commented Apr 3, 2025

Sorry, but I've seen your approvement and both change requests have been addressed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants